Apple, the Apple logo, and Macintosh are registered trademarks of Apple Computer, Inc.
Mac and OpenDoc are trademarks of Apple Computer, Inc.
Document Exchange
OpenDoc is intended to be a cross-platform architecture. Document Exchange is a general term referring to the ability for any platform to manipulate documents that are created on the same or other platform.
User-visible string: kODIntlTxt (ISO 10646,1993UCS standard)
Transform: 3x3 Fixed, 16.16
Shape: Polygon
Persistent Reference: Array of 4 bytes (NOT long)
Icon: ODIconData
Endianess:
All OpenDoc meta-data is stored in little endian.
Alignment:
Natural Alignment (i.e., 8-bit Boundaries for bytes, 16-bit boundaries for 16-bit types and 32-bit boundaries for 32 bit types.)
Coordinate system:
ODPoint uses 16.16 Fixed and the default top-level coordinate system for an OpenDoc Document is one unit equals 1/72 of an inch.
Implications to Parts:
OpenDoc meta-data and parts:
In general, parts do not have to worry about the OpenDoc meta-data. The API hides most of the cross-platform details from the parts. For example, An ODShape associated with an ODFrame is stored persistently in little-endian format. When the frame internalizes the shape, it will do the necessary conversion so that the runtime ODShape object uses the endianess favored by the platform. Only when a part needs to access the OpenDoc meta-data stored in persistent storage directly does it have to worry about the persistent document exchange format.
Cross-platform parts:
Parts have complete control over their data format. Therefore, they don’t have to follow the same standard as OpenDoc meta-data. However, one should try to make one’s part as inspectable on persistent storage as possible.